Thank you for contributing to Coraza WAF, your effort is greatly appreciated
Before submitting check if what you want to add to coraza list meets quality standards before sending pull request. Thanks!

Make sure that you've checked the boxes below before you submit PR:

• My code includes positive and negative tests.
• I have an appropriate description with correct grammar.
• I have read Contribution guidelines, maintainers note and Quality standard.
• My code is properly linted and passes pre-commit tests.

#923 introduced a stackoverflow when the value passed to ReadFrom does not implement the io.WriterTo interface.

From the go stdlib source :

// copyBuffer is the actual implementation of Copy and CopyBuffer.
// if buf is nil, one is allocated.
func copyBuffer(dst Writer, src Reader, buf []byte) (written int64, err error) {
	// If the reader has a WriteTo method, use it to do the copy.
	// Avoids an allocation and a copy.
	if wt, ok := src.(WriterTo); ok {
		return wt.WriteTo(dst)
	}
	// Similarly, if the writer has a ReadFrom method, use it to do the copy.
	if rt, ok := dst.(ReaderFrom); ok {
		return rt.ReadFrom(src)
	}

If the first optimization can run no stackoverflow will happen.
But if the src does not implement io.WriterTo it will go to a second optimization.

In our use case it triggers a stackoverflow by calling itself.

There might be other ways to fix this and any suggestions are welcome!
I chose to erase all interfaces from the ResponseWriter except io.Writer.

This forces io.Copy to use Write(), which was the intended behavior.